(1.37.109.15/16.2) id AA188232344; Sat, 21 Oct 1995 20:25:44 -0700
Return-Path: <owner-lightwave@mail.webcom.com>
Received: from shadow.net (anshar.shadow.net) by mail.webcom.com with ESMTP
(1.37.109.15/16.2) id AA188172337; Sat, 21 Oct 1995 20:25:37 -0700
Received: from ppp-mia-65.shadow.net (ppp-mia-65.shadow.net [198.79.48.65]) by shadow.net (8.6.12/8.6.12) with SMTP id XAA12154 for <lightwave@webcom.com>; Sat, 21 Oct 1995 23:13:47 -0400
Date: Sat, 21 Oct 1995 23:13:47 -0400
Message-Id: <199510220313.XAA12154@shadow.net>
X-Sender: jdunfee@shadow.net
X-Mailer: Windows Eudora Version 1.4.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: lightwave@mail.webcom.com
From: jdunfee@shadow.net (Joe Dunfee)
Subject: Bug List
Sender: owner-lightwave@mail.webcom.com
Precedence: bulk
When I was speaking with NewTek about the bugs in the DXF export feature,
I ask if there was a bug list available anywhere. He said that don't have a
bug list. Of course, I assume he meant that they don't have a bug list that
they will release to the public.
This was a complaint against AutoDesk for many years. Autodesk's argument
was that to release a bug list was equivalent to giving amunition to the
competition. However, we the users felt very different. We felt that
Autodesk was deliberately concealing known bugs and as a result, we the
users had to "accidentally" discover the bugs. This would occasionally
involve many hours of work and frustration, and in a few cases, drawings
were lost or destroyed in the process. We would end up contacting Autodesk
after all this only to find out that this was a known bug and there was a
simple work around.
WHY WOULDN'T THEY TELL US THIS BEFORE WE
WENT THROUGH ALL THIS FRUSTRATION!!
There is only one answer... they just didn't care. However, finally they
came to their senses after enough irate customers voiced their opinions. I
first searched their FTP sight looking for a solution for my DXF exporting
delema... Nothing there.I searched back issues of this newsgroup... again
nothing. I called their technical support (after holding for about 10
minutes, they took my name and number and called me back later that day)
Their Tech guy said his worked fine, but it was a later version than mine.
He directed me to Syndesis company, which agreed to E-Mail me the fix.
NewTek has the solution for the problem, but require you to discover the
problem yourself and take an un-necessary series of steps to get the fix.
Why not release a bug list with any suggested work arounds (perhaps even by
way of a small newsletter) and make any fixes available to the public via
FTP or their BBS? This will eliminate a major cause of irate customers.
Joe Dunfee,
Miami, Florida USA
--
jdunfee@shadow.net (Joe Dunfee) sent this message.
To Post a Message : lightwave@webcom.com
Un/Subscription Requests To : lightwave-request@webcom.com
(DIGEST) or : lightwave-digest-request@webcom.com
Administrative Items To : owner-lightwave@webcom.com